- 
                Notifications
    You must be signed in to change notification settings 
- Fork 64
          feat: add GeoSeries.difference() and bigframes.bigquery.st_difference()
          #1471
        
          New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
          
     Merged
      
      
    Conversation
  
    
      This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
      Learn more about bidirectional Unicode characters
    
  
  
    
    | Check out this pull request on   See visual diffs & provide feedback on Jupyter Notebooks. Powered by ReviewNB | 
…nore the exception
              
                    tswast
  
              
              reviewed
              
                  
                    Mar 18, 2025 
                  
              
              
            
            
GeoSeries.difference()bigframes.geopandas.GeoSeries.difference() and bigframes.bigquery.st_difference()`
      bigframes.geopandas.GeoSeries.difference() and bigframes.bigquery.st_difference()`bigframes.geopandas.GeoSeries.difference() and bigframes.bigquery.st_difference()
      bigframes.geopandas.GeoSeries.difference() and bigframes.bigquery.st_difference()GeoSeries.difference() and bigquery.st_difference()
      GeoSeries.difference() and bigquery.st_difference()GeoSeries.difference() and bigframes.bigquery.st_difference()
      | e2e failures: I'm not seeing anything geo-related, so I think these are all unrelated. | 
              
                    tswast
  
              
              approved these changes
              
                  
                    Mar 21, 2025 
                  
              
              
            
            
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Very cool!
    
  shobsi 
      pushed a commit
      that referenced
      this pull request
    
      Mar 28, 2025 
    
    
      
  
    
      
    
  
…nce()` (#1471) * feat: add GeoSeries.difference() * add st_difference method and test cases for geo.difference and st_difference * update method and tests * update method and tests * update test to cover different inputs * update test assertion * update testing with single geometry object and add notebook tag to ignore the exception * fix docstrings * modify geo_difference to make it available for use and update tests and notebook * fix my py type error
  
    Sign up for free
    to join this conversation on GitHub.
    Already have an account?
    Sign in to comment
  
      Labels
      
    api: bigquery
  Issues related to the googleapis/python-bigquery-dataframes API. 
  
    size: l
  Pull request size is large. 
  Add this suggestion to a batch that can be applied as a single commit.
  This suggestion is invalid because no changes were made to the code.
  Suggestions cannot be applied while the pull request is closed.
  Suggestions cannot be applied while viewing a subset of changes.
  Only one suggestion per line can be applied in a batch.
  Add this suggestion to a batch that can be applied as a single commit.
  Applying suggestions on deleted lines is not supported.
  You must change the existing code in this line in order to create a valid suggestion.
  Outdated suggestions cannot be applied.
  This suggestion has been applied or marked resolved.
  Suggestions cannot be applied from pending reviews.
  Suggestions cannot be applied on multi-line comments.
  Suggestions cannot be applied while the pull request is queued to merge.
  Suggestion cannot be applied right now. Please check back later.
  
    
  
    
Thank you for opening a Pull Request! Before submitting your PR, there are a few things you can do to make sure it goes smoothly:
Fixes #<issue_number_goes_here> 🦕